SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Emergent Coding</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Emergent Coding</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}

/* end https://en.wikipedia.org/ */

</style><table class="infobox vevent"><tbody><tr><th colspan="2" class="infobox-above" style="background-color:#e0e0e0;">Emergent Coding</th></tr><tr><td colspan="2" class="infobox-image"><span typeof="mw:File"></span><div class="infobox-caption">Emergent Coding Official Logo</div></td></tr><tr><th scope="row" class="infobox-label"><a href="Programming_paradigm" title="Programming paradigm">Paradigm</a></th><td class="infobox-data">Components based, Distributed Decentralized Development, Software Components Market</td></tr><tr><th scope="row" class="infobox-label"><a href="Software_design" title="Software design">Designed by</a></th><td class="infobox-data">Noel Lovisa</td></tr><tr><th scope="row" class="infobox-label"><a href="Software_developer" class="mw-redirect" title="Software developer">Developer</a></th><td class="infobox-data organiser">Code Valley</td></tr><tr><th scope="row" class="infobox-label">First appeared</th><td class="infobox-data">2000<span style="display:none"> (<span class="bday dtstart published updated">2000</span>)</span></td></tr><tr><td colspan="2" class="infobox-full-data"></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;"><a href="Software_release_life_cycle" title="Software release life cycle">Stable release</a></th><td class="infobox-data"><div style="margin:0px;">G29

/ TBD</div></td></tr><tr style="display:none"><td colspan="2">

</td></tr><tr><th scope="row" class="infobox-label"><a href="Type_system" title="Type system">Typing discipline</a></th><td class="infobox-data">NA</td></tr><tr><th scope="row" class="infobox-label"><a href="Scope_(computer_science)" title="Scope (computer science)">Scope</a></th><td class="infobox-data">NA</td></tr><tr><th scope="row" class="infobox-label"><a href="Operating_system" title="Operating system">OS</a></th><td class="infobox-data"><a href="Mac_OS" class="mw-redirect" title="Mac OS">Mac OS</a>, <a href="Linux" title="Linux">Linux</a></td></tr><tr><th scope="row" class="infobox-label"><a href="Software_license" title="Software license">License</a></th><td class="infobox-data">Emergent Coding License</td></tr><tr><th scope="row" class="infobox-label"><a href="Filename_extension" title="Filename extension">Filename extensions</a></th><td class="infobox-data">.ap, .elf</td></tr><tr><th scope="row" class="infobox-label">Website</th><td class="infobox-data"><span class="url"><a rel="nofollow" class="external text" href="https://www.codevalley.com/">www<wbr>.codevalley<wbr>.com</a></span></td></tr></tbody></table>

<p><b>Emergent Coding</b> is a <a href="Decentralization" title="Decentralization">decentralized</a> <a href="Software_development" title="Software development">software development</a> paradigm employing a type of <a href="Software_component" title="Software component">software component</a> that cannot be copied or reused with the objective of achieving both workable developer specialization, and a practical software components market.<sup id="cite_ref-CodeValley_1-0" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-McIlroy_2-0" class="reference"><a href="#cite_note-McIlroy-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Description">Description</h2></div>

<p>Emergent Coding is a <a href="Decentralization" title="Decentralization">decentralized</a> <a href="Software_development" title="Software development">software development</a> paradigm employing a new type of software component that cannot be copied or reused.<sup id="cite_ref-CodeValley_1-1" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> The method ensures developers can safely list their software components for public sale without endangering prospects for <a href="Customer_retention" title="Customer retention">repeat business</a>,<sup id="cite_ref-ACM_3-0" class="reference"><a href="#cite_note-ACM-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> a feature essential for both workable developer specialization, and realizing <a href="Douglas_McIlroy" title="Douglas McIlroy">Douglas McIlroy's</a> 1968 vision of a software components market.<sup id="cite_ref-McIlroy_2-1" class="reference"><a href="#cite_note-McIlroy-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p><p>The change is a reversal of integration responsibility such that instead of fetching a component in a traditional sense, a developer provides a project construction-site to the supplier with that supplier now integrating their component into the project. The reversal switches the view of components from a <a href="Library_(computing)" title="Library (computing)">library</a>-of-routines to a <a href="Cataloging" class="mw-redirect" title="Cataloging">catalogue</a>-of-design-services.<sup id="cite_ref-CodeValley_1-2" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p><p>The reversal permits this new component type to properly scale as the construction-site can be readily partitioned to engage sub-contractors allowing components to be fielded as an assemblage of smaller ones which do likewise. Scaling down allows small components to absorb the role of the traditional <a href="Compiler" title="Compiler">compiler</a>, removing its <a href="Centralism" class="mw-redirect" title="Centralism">centralism</a> from software development while scaling up results in <a href="Domain-specific_language" title="Domain-specific language">domain-specific</a> components for expressing project <a href="Software_requirements" title="Software requirements">requirements</a>.<sup id="cite_ref-CodeValley_1-3" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p><a href="Douglas_McIlroy" title="Douglas McIlroy">Douglas McIlroy</a> at a <a href="NATO" title="NATO">NATO</a> conference in 1968, observed: "The Software Industry is Not Industrialized"<sup id="cite_ref-McIlroy_2-2" class="reference"><a href="#cite_note-McIlroy-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> and proposed a software components market with component "distribution by <a href="Communication_link" class="mw-redirect" title="Communication link">communication link</a>” whereby “even very small components might be profitably marketed". McIlroy imagined a "<a href="Sears-Roebuck" class="mw-redirect" title="Sears-Roebuck">Sears-Roebuck</a>" style catalogue "to have for [his] own were [he] purchasing components." McIlroy's proposal did not address how viable developer specialization might come about if we are to turn our "<a href="Crofters" class="mw-redirect" title="Crofters">crofters</a>" into "<a href="Industrialists" class="mw-redirect" title="Industrialists">industrialists</a>". Specifically, while it is easy for a developer to specialize, it is virtually impossible for them to build a viable business as a specialist.

</p><p>In late 1994, Noel Lovisa proposed reversing the integration responsibility as a means of shielding supplier <a href="Intellectual_property" title="Intellectual property">intellectual property</a>, thereby preserving prospects for repeat business, and establishing a workable basis for developer specialization. Lovisa founded Code Valley Corp Pty Ltd<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> in May 2000 to create and field a practical software components market based on the principal, releasing a white paper in 2016,<sup id="cite_ref-CodeValley_1-4" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> and conducting trials of a centralized software components market that same year. In June 2018, Lovisa delivered a keynote address at <a href="International_Conference_on_Software_Engineering" title="International Conference on Software Engineering">ICSE 2018</a> in <a href="Gothenburg" title="Gothenburg">Gothenburg</a>, <a href="Sweden" title="Sweden">Sweden</a><sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> which, being the 50th anniversary of the 1968 <a href="NATO_Software_Engineering_Conferences" title="NATO Software Engineering Conferences">NATO Software Engineering Conference</a>,<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-McIlroy_2-3" class="reference"><a href="#cite_note-McIlroy-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> was attended by McIlroy and other industry leaders. In September 2023, McIlroy extended an invitation to Lovisa to present Emergent Coding at <a href="Dartmouth_College" title="Dartmouth College">Dartmouth College</a>, New Hampshire.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p><p>In late 2023, Code Valley began trials of a decentralized and fully non-custodial software components market featuring a custom <a href="Integrated_development_environment" title="Integrated development environment">Integrated Development Environment</a> (IDE), over 5000 software components occupying 4 levels of <a href="Abstraction_(computer_science)" title="Abstraction (computer science)">abstraction</a> (Behaviour, Systems, Data, Byte), a Distributed Fault Tracing System (DFT), a <a href="Peer-to-peer" title="Peer-to-peer">peer-to-peer</a> <a href="Bitcoin_Cash" title="Bitcoin Cash">electronic cash</a> payment system, and an interactive catalogue of component prices, data sheets, contract specifications, and reference designs.

</p><p>The implementation, itself built with emergent coding, is expected to publicly launch in 2025.

</p>

<div class="mw-heading mw-heading2"><h2 id="Emergent_Coding_Software_Development">Emergent Coding Software Development</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tmulti .multiimageinner{display:flex;flex-direction:column}.mw-parser-output .tmulti .trow{display:flex;flex-direction:row;clear:left;flex-wrap:wrap;width:100%;box-sizing:border-box}.mw-parser-output .tmulti .tsingle{margin:1px;float:left}.mw-parser-output .tmulti .theader{clear:both;font-weight:bold;text-align:center;align-self:center;background-color:transparent;width:100%}.mw-parser-output .tmulti .thumbcaption{background-color:transparent}.mw-parser-output .tmulti .text-align-left{text-align:left}.mw-parser-output .tmulti .text-align-right{text-align:right}.mw-parser-output .tmulti .text-align-center{text-align:center}@media all and (max-width:720px){.mw-parser-output .tmulti .thumbinner{width:100%!important;box-sizing:border-box;max-width:none!important;align-items:center}.mw-parser-output .tmulti .trow{justify-content:center}.mw-parser-output .tmulti .tsingle{float:none!important;max-width:100%!important;box-sizing:border-box;text-align:center}.mw-parser-output .tmulti .tsingle .thumbcaption{text-align:left}.mw-parser-output .tmulti .trow>.thumbcaption{text-align:center}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .tmulti .multiimageinner span:not(.skin-invert-image):not(.skin-invert):not(.bg-transparent) img{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .tmulti .multiimageinner span:not(.skin-invert-image):not(.skin-invert):not(.bg-transparent) img{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="thumb tmulti tright"><div class="thumbinner multiimageinner" style="width:354px;max-width:354px"><div class="trow"><div class="tsingle" style="width:352px;max-width:352px"><div class="thumbimage"><span typeof="mw:File"></span></div></div></div><div class="trow" style="display:flex"><div class="thumbcaption">Emergent Coding Integrated Development Environment (IDE)</div></div></div></div>

<p>Component Based Software development begins with drafting an expression containing a series of contract statements for engaging the desired component suppliers assisted by the contract specifications published in the component catalogue. As all components in the catalogue have a listed price, the total cost of the project can be reliably determined from the expression before committing to construction. When the expression is deemed in order and the costs acceptable, the project can be built. During the build process, the IDE <a href="Parsing" title="Parsing">parses</a> the expression and engages the contractors by forwarding contracts and payments to each. These <a href="Contractors" class="mw-redirect" title="Contractors">contractors</a> receive a portion of their requirements via their contract terms directly with the balance determined via collaboration between contractors as authorized by the contract terms. Each component contractor concludes their contract by returning a fragment of code and data that when concatenated, forms the resultant project binary.<sup id="cite_ref-CodeValley_1-5" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p><p>Each contractor engaged, verifies payment and allocates a job against the contract, being sure to return the job number to the client so they may forward communication authorizations for the collaborations between contractors as detailed in the expression. These contractors receive a portion of their requirements via their contract terms directly with the balance determined via collaboration with peers as authorized by the contract terms. Once in possession of project requirements, each <a href="Subcontractor" title="Subcontractor">sub-contracts</a> smaller components as directed by their <a href="Design_knowledge" title="Design knowledge">special knowledge</a>, which do likewise. Each component subcontractor returns a fragment of code and data that when concatenated, form single code and data fragments for receipt to the client concluding the contract.<sup id="cite_ref-CodeValley_1-6" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p><p><a href="Leaf_nodes" class="mw-redirect" title="Leaf nodes">Leaf</a> contractors in the project contracting <a href="Tree_(data_structure)" class="mw-redirect" title="Tree (data structure)">tree</a> similarly verify payment and allocate a job against the contract, being sure to return the job number to the client so they may forward communication authorizations for the collaborations between contractors as detailed by their special knowledge. As before, these contractors receive a portion of their requirements via their contract terms directly with the balance determined via collaboration with peers as authorized by the contract terms, however, as a result of gaining sufficient understanding of their design-time context, they render their code and data fragments directly for receipt to the client concluding the contract.<sup id="cite_ref-CodeValley_1-7" class="reference"><a href="#cite_note-CodeValley-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li><a href="Component-based_software_engineering" title="Component-based software engineering">component-based software engineering</a></li>

<li><a href="Software_product_line_engineering" class="mw-redirect" title="Software product line engineering">software product line engineering</a></li>

<li><a href="Comparison_of_programming_languages" title="Comparison of programming languages">Comparison of programming languages</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-lower-alpha">

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.codevalley.com/">"Emergent Coding Whitepaper, available on website"</a>. Code Valley<span class="reference-accessdate">. Retrieved <span class="nowrap">6 August</span> 2024</span>.</cite></span>

</li>

<li id="cite_note-McIlroy-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-McIlroy_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-McIlroy_2-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-McIlroy_2-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-McIlroy_2-3"><sup><i><b>d</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFMcIlroy1968" class="citation journal cs1">McIlroy, Douglas (11 October 1968). <a rel="nofollow" class="external text" href="https://www.cs.dartmouth.edu/~doug/components.txt">"MASS PRODUCED SOFTWARE COMPONENTS"</a>. <i>Software Engineering, Report on a conference sponsored by the NATO Science Committee, Garmisch, Germany</i><span class="reference-accessdate">. Retrieved <span class="nowrap">6 August</span> 2024</span>.</cite></span>

</li>

<li id="cite_note-ACM-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-ACM_3-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFVitharana" class="citation web cs1">Vitharana, Padmal. <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/pdf/10.1145/859670.859671">"Risks and Challenges of Component-based Software Development"</a>. <i>ACM.org</i>. Communications of the ACM<span class="reference-accessdate">. Retrieved <span class="nowrap">30 September</span> 2024</span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://abr.business.gov.au/ABN/View/70093129894">"Australian Business Register"</a>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.youtube.com/watch?v=siJQVk5jkbo&t=26s">"Live from ICSE: Industry Forum - Noel Lovisa"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">19 September</span> 2024</span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://conf.researchr.org/home/icse-2018">"ICSE 2018"</a>. <i>40th International Conference on Software Engineering, May 27–3 June 2018, Gothenburg, Sweden</i>.</cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF">"Software Engineering"</a> <span class="cs1-format">(PDF)</span>.</cite></span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1969.PDF">"Software Engineering Techniques"</a> (PDF)</span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://web.cs.dartmouth.edu/events/event?event=71455">"Emergent coding – a radical model of software development"</a>. 15 September 2023<span class="reference-accessdate">. Retrieved <span class="nowrap">19 September</span> 2024</span>.</cite></span>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-01-30" href="https://en.wikipedia.org/wiki/?title=Emergent_Coding&oldid=1272883334">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>